Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Do not pass the module_repository in PE >=3.2 #190

Closed
wants to merge 1 commit into from
Closed

Do not pass the module_repository in PE >=3.2 #190

wants to merge 1 commit into from

Conversation

adreyer
Copy link

@adreyer adreyer commented Mar 27, 2014

These versions of Puppet Enterprise talk to the v3 forge API which is
not present at http://forge.puppetlabs.com which is the default in
Puppetfiles created by librarian puppet. This will break installs from
pulp and should be reconsidered when pulp and librarian-puppet are
updated to support the v3 forge api(https://forgeapi.puppetlabs.com).

In addition newer versions of PMT enforce some additional rules when
installing modules that probably don't make sense if validation is being
done inside librarian-puppet. Instead of --ignore-dependencies librarian
should use --force.

These versions of Puppet Enterprise talk to the v3 forge API which is
not present at http://forge.puppetlabs.com which is the default in
Puppetfiles created by librarian puppet. This will break installs from
pulp and should be reconsidered when pulp and librarian-puppet are
updated to support the v3 forge api(https://forgeapi.puppetlabs.com).

In addition newer versions of PMT enforce some additional rules when
installing modules that probably don't make sense if validation is being
done inside librarian-puppet. Instead of --ignore-dependencies librarian
should use --force.
@curator
Copy link

curator commented Apr 1, 2014

I'd like to throw my support for this pull request in here as we're an org currently affected by the issue. Right now we're using a hand-rolled LP, but would love to move back to the community gem.

@carlossg
Copy link
Collaborator

carlossg commented Apr 3, 2014

Thanks for the PR. I've implemented it a bit differently to handle the v3 api, can you check that the branch api-v3 looks good for you?
https://github.com/rodjek/librarian-puppet/compare/api-v3

@adreyer
Copy link
Author

adreyer commented Apr 3, 2014

This change was in 3.2.0 so the following should be >= not > I think.

if pe_version and Gem::Version.create(pe_version[1].strip) > Gem::Version.create('3.2.0')

Other than that it looks fine.

@carlossg
Copy link
Collaborator

carlossg commented Apr 3, 2014

gotcha, thanks. Trying to release 1.0.0 and then this goes next

@MasonM
Copy link

MasonM commented Apr 9, 2014

@carlossg I tried out your branch with PE 3.2.1 and it didn't work (see my comment at 55c01cd). @adreyer's branch did work, though.

@carlossg
Copy link
Collaborator

carlossg commented Apr 9, 2014

@MasonM I noticed the error, and had to merge the latest changes in master, can you check api-v3 again? If that looks good I'll merge and release

@MasonM
Copy link

MasonM commented Apr 9, 2014

@carlossg Yep, those latest commits fixed it. Thanks!

carlossg pushed a commit that referenced this pull request Apr 12, 2014
…3 API

Swap http://forge.puppetlabs.com to https://forgeapi.puppetlabs.com on the fly
Avoid executing puppet several times
Create a new puppet_gem_version method for comparisons
@carlossg
Copy link
Collaborator

Merged in bd29b9f

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants